Method, apparatus, and system for providing ride-sharing functions based on joint motion

ABSTRACT

An approach is provided for performing ride-sharing functions based on joint motion using multiple sensor data. The approach, for example, involves retrieving a joint motion prediction indicating whether at least two devices are traveling in a same transportation vehicle. The joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types. Each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction. The approach also involves initiating a ride-sharing function for respective users of the at least two devices based on the joint motion prediction.

BACKGROUND

Service providers are continually challenged to provide new and compelling services. One area of development relates to developing services based on detecting whether two or more people are traveling together in the same transportation vehicle (e.g., car, bus, train, etc.). Accordingly, service providers face significant technical challenges to enable automatic and accurate detection of joint motion (e.g., traveling together in the same vehicle) between two or more people or devices, and then providing service functions based on the detected joint motion detection.

SOME EXAMPLE EMBODIMENTS

Therefore, there is a need for an approach for detecting joint motion using sensor data collected from mobile devices and then using the joint motion prediction or detection for providing services such as but not limited to ride-sharing, social networking, and point-of-interest detection/classification. It is noted that as used herein the terms “joint motion prediction” and “joint motion detection” are used interchangeably to refer to classifying two more users a traveling together in the same vehicle.

According to one embodiment, a method comprises retrieving a joint motion prediction indicating whether at least two devices are traveling in a same transportation vehicle. The joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types. Each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction. Said prediction can be computed by classifiers for which the input is said sensor type classifiers and processing thereof. The method also comprises initiating or altering a ride-sharing function for respective users of the at least two devices based on the joint motion prediction.

According to another embodiment, an apparatus comprises at least one processor, and at least one memory including computer program code for one or more computer programs, the at least one memory and the computer program code configured to, with the at least one processor, cause, at least in part, the apparatus to retrieve a joint motion prediction indicating whether at least two devices are traveling in a same transportation vehicle. The joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types. Each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction. Said prediction can be computed by classifiers for which the input is said sensor type classifiers and processing thereof. The apparatus is also caused to initiate or alter a ride-sharing function for respective users of the at least two devices based on the joint motion prediction.

According to another embodiment, a computer-readable storage medium carries one or more sequences of one or more instructions which, when executed by one or more processors, cause, at least in part, an apparatus to retrieve a joint motion prediction indicating whether at least two devices are traveling in a same transportation vehicle. The joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types. Each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction. Said prediction can be computed by classifiers for which the input is said sensor type classifiers and processing thereof. The apparatus is also caused to initiate or alter a ride-sharing function for respective users of the at least two devices based on the joint motion prediction.

According to another embodiment, an apparatus comprises means for retrieving a joint motion prediction indicating whether at least two devices are traveling in a same transportation vehicle. The joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types. Each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction. Said prediction can be computed by classifiers for which the input is said sensor type classifiers and processing thereof. The apparatus also comprises means for initiating or altering a ride-sharing function for respective users of the at least two devices based on the joint motion prediction.

In addition, for various example embodiments of the invention, the following is applicable: a method comprising facilitating a processing of and/or processing (1) data and/or (2) information and/or (3) at least one signal, the (1) data and/or (2) information and/or (3) at least one signal based, at least in part, on (or derived at least in part from) any one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.

For various example embodiments of the invention, the following is also applicable: a method comprising facilitating access to at least one interface configured to allow access to at least one service, the at least one service configured to perform any one or any combination of network or service provider methods (or processes) disclosed in this application.

For various example embodiments of the invention, the following is also applicable: a method comprising facilitating creating and/or facilitating modifying (1) at least one device user interface element and/or (2) at least one device user interface functionality, the (1) at least one device user interface element and/or (2) at least one device user interface functionality based, at least in part, on data and/or information resulting from one or any combination of methods or processes disclosed in this application as relevant to any embodiment of the invention, and/or at least one signal resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.

For various example embodiments of the invention, the following is also applicable: a method comprising creating and/or modifying (1) at least one device user interface element and/or (2) at least one device user interface functionality, the (1) at least one device user interface element and/or (2) at least one device user interface functionality based at least in part on data and/or information resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention, and/or at least one signal resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.

In various example embodiments, the methods (or processes) can be accomplished on the service provider side or on the mobile device side or in any shared way between service provider and mobile device with actions being performed on both sides.

For various example embodiments, the following is applicable: An apparatus comprising means for performing a method of any of the claims.

Still other aspects, features, and advantages of the invention are readily apparent from the following detailed description, simply by illustrating a number of particular embodiments and implementations, including the best mode contemplated for carrying out the invention. The invention is also capable of other and different embodiments, and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the invention. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings:

FIG. 1 is a diagram of a system capable of detecting joint motion using multiple sensor data, according to one embodiment;

FIGS. 2A and 2B are diagrams illustrating examples of a joint motion and separate motion respectively, according to one embodiment;

FIG. 3 is table illustrating examples of computing a unified joint motion prediction from sensor-specific joint motion predictions, according to one embodiment;

FIG. 4 is a diagram of components of a joint motion platform, according to one embodiment;

FIG. 5 is a flowchart of a process for detecting joint motion using multiple sensor data, according to one embodiment;

FIGS. 6A-6D are graphs illustrating examples of location-based joint motion predictions for use in computing a unified joint motion prediction;

FIGS. 7A and 7B are graphs illustrating example correlations of sensor-specific joint predictions for use in computing a unified joint motion prediction;

FIG. 8 illustrates an example user interface for presenting a unified joint motion prediction based on multiple sensor data, according to one embodiment;

FIG. 9 is a flowchart of a process for providing ride-sharing functions based on joint motion detected using multiple sensor data, according to one embodiment;

FIGS. 10A-10F are diagrams of example user interfaces for providing ride-sharing functions based on joint motion, according to various embodiments;

FIG. 11 is a flowchart of a process for providing social networking functions based on joint motion detected using multiple sensor data, according to one embodiment;

FIGS. 12A and 12B are diagrams of example user interfaces for providing social networking functions based on joint motion, according to various embodiments;

FIG. 13 is a flowchart of a process for providing point of interest (POI) detection and/or classification using joint motion, according to one embodiment;

FIGS. 14A and 14B are diagrams of example user interfaces for providing POI detection and/or classification based on joint motion, according to various embodiments

FIG. 15 is a diagram of a geographic database, according to one embodiment;

FIG. 16 is a diagram of hardware that can be used to implement an embodiment;

FIG. 17 is a diagram of a chip set that can be used to implement an embodiment; and

FIG. 18 is a diagram of a mobile terminal that can be used to implement an embodiment.

DESCRIPTION OF SOME EMBODIMENTS

Examples of a method, apparatus, and computer program for detecting joint motion using multiple sensor data are disclosed. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It is apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention.

FIG. 1 is a diagram of a system capable of detecting joint motion using multiple sensor data, according to one embodiment. As discussed above, automatically detecting when two or more people or devices (e.g., user equipment (UE) devices 101 a-101 n—also referred to as UEs 101—such as phones, tablets, computers, etc. with internet connectivity) are sharing the same transportation vehicle 103 (e.g., car, bus, train, airplane, etc.). This state of sharing or otherwise being in the same transportation vehicle 103 is referred to herein as joint motion (JM) between the two people or UEs 101.

One approach to determining JM or joint path identification is based on location data only (e.g., obtained from location sensors such as but not limited to Global Positioning System (GPS) receivers). However, in many cases location data is not available or inaccurate due to poor reception (e.g. disturbances of the GPS signal from buildings, tunnels, etc.), and JM or proximity is not detected (“false negative”). Moreover, location-based approaches generally cannot account for “false positive” situations. One example of a false positive situation is illustrated in FIGS. 2A and 2B. As shown in example 200 of FIG. 2A, a location data only approach may detect a false positive situation where it determines that two devices (e.g., UEs 101 a and UE 101 b) are in the same vehicle 201 when instead the true situation is illustrated in example 220 of FIG. 2B where the two UEs 101 a and 101 b are traveling in different respective vehicles 221 a and 221 b.

This is because location data only approaches typically compare how closely the location paths of the UEs 101 a and 101 b are located with respect to each other to determine JM. However, the location data only may not be able to distinguish between the situations of FIG. 2A and FIG. 2B under some circumstances such as where two cars are driving nearby for extended periods of time, as occurring, for instance, in traffic jams or when two cars are following each other closely. In addition, due to the limited accuracy of location information in mobile devices (e.g., typically 10-20 m in good conditions), location data only approaches may falsely detect nearby people or devices as potential JM. As a result, service providers face significant technical challenges to more accurately detecting JM states between people or devices.

To address these technical challenges, the system 100 of FIG. 1 introduces a capability to determine whether two or more people or devices (e.g., UEs 101) are sharing the same transportation vehicle 103 (e.g., car, bus, train, airplane, boat, etc.), based on information extracted from the sensing capabilities external to or separate from traditional positioning sensors (e.g., Global Positioning System (GPS), Global Navigation Satellite System (GNSS), Inertial Measurement Unit (IMU), and/or the like) of mobile devices, such as but not limited to phones and tablets with internet connectivity (e.g., UEs 101 equipped with multiple sensors 105 a-105 m of different types that sensed different physical characteristics). In one embodiment, the system 100 makes use of several different types of sensors 105, typically found in mobile devices, to collect sensor data 107 and then make individual JM predictions for each sensor type. The individual JM predictions can then be combined by the JM platform 109 to make a unified JM prediction to provide an effective solution in discovering JM behavior. The unified JM predictions or detected JM behaviors can then be output or stored as JM data 111.

The combination of predictions made from different types of sensor data streams provides for several advantages including but not limited to: (1) JM can be determined even in the absence of location data and/or inertial measurement unit (IMU) data; and (2) ability to distinguish between true JM and multiple people or devices moving separately nearby to one another, e.g., like in traffic jams.

In one embodiment, the system 100 uses different JM classifiers optimized for each sensor data type to make individual JM predictions (e.g., individual with respect to each different sensor type). Optimized, for instance, refers to creating or training a classifier (e.g., in the case of machine learning based classifiers) to recognize or take advantage of features or algorithms specific to each type of sensor data being used. A unified classifier (e.g., a state machine, voting algorithm, and/or the like) controls the different sensor-specific JM classifiers and integrates the data (e.g., individual JM predictions) from the available sensor-specific classifiers into a single result. In one embodiment, the JM classifiers used by the system 100 can include JM classifiers based on location data and/or IMU data if, e.g., GPS/GNSS and/or IMU data are available. When such GPS/GNSS and/or IMU are not available (e.g., when operating in areas with interference such as urban canyons, indoor environments, etc.), the system 100 can use JM classifiers that input sensor data from sensors 105 other than GPS/GNSS, IMU, and/or any other type of sensors 105 that provide location or motion as an output value.

The system 100 can integrate any number of sensor-specific JM classifiers including but not limited to any combination of two or more of the components described below:

-   -   Location data-based classifier—Using location data derived from         GPS/GNSS, cellular towers, WIFI, and/or equivalent location         sensors. The underlying assumption here is that close-proximity         between two UEs 101 for an extended period (e.g., a period         longer threshold duration) is a characteristic of JM. In one         embodiment, a variant of the location-based classifier for JM         comprises using partial location raw data which do not allow for         location determination or for accurate location determination,         but still suffice to determine JM accurately.     -   IMU based classifier—Using data from accelerometers, gyroscopes,         magnetometers, and/or equivalent IMU sensors. IMU sensor data of         two devices moving together is naturally correlated for the         duration of their joint journey.     -   Barometer based classifier—To be used similarly to IMU data         except with data collected from barometric sensors. Close         correlation barometric data between two UEs 101 for an extended         period (e.g., a period longer than a threshold duration) is a         characteristic of JM.     -   Bluetooth based classifier—Two Bluetooth equipped UEs 101         sensing the received signal strength indication (RSSI) of the         other Bluetooth device are very likely to be in nearby (“active         BT”). Therefore, close-proximity between two UEs 101 for an         extended period (e.g., a period longer than a threshold         duration) is a characteristic of JM. In one embodiment, a         variant of the Bluetooth based classified is based on two         Bluetooth equipped UEs 101 sensing concurrently a third         transmitting Bluetooth device (“passive BT”).     -   Near Field Communication (NFC) based classifier—Using data on         nearby NFC devices. Given two UEs 101 that can communicate via         NFC, the NFC based classifier that the NFC communication         connection indicates a proximity of the two UEs 101 of up to 20         cm or other specified NFC range. Close proximity between two UEs         101 for an extended period (e.g., a period longer than a         threshold duration) is a characteristic of JM.     -   Acoustics based classifier—Using active or passive acoustics         data to identify two UEs 101 in near proximity. Close proximity         between two UEs 101 for an extended period (e.g., a period         longer than a threshold duration) is a characteristic of JM.     -   Maps based meta data classifier—Using map-based data (e.g., as         stored in the geographic database 113) can significantly         increase prediction quality by providing boundaries on         limitations against which JM predictions can be checked. For         example, since pickup and drop-off events are unlikely in         certain places like highways or tunnels JM motions events are         unlikely to start or stop at these locations. Therefore, if JM         is detected to start or stop at one of these locations as         indicated by the geographic database 113, the classifier can         reject the prediction.

FIG. 3 illustrates a table 300 that provides examples of computing a unified joint motion prediction from sensor-specific joint motion predictions, according to one embodiment. In the example of FIG. 3, the system 100 employs six sensor-specific JM classifiers (e.g., location based, accelerometer correlation based, Bluetooth (BT) based, NFC based, Acoustic based, and local magnetic field based) that can be combined to provide a unified JM prediction. Each classifier processes sensor data collected from respective sensor types to make individual predictions of joint motion (e.g., “+” indicating JM, “−” indicating separate motion, and “+/−” indicating insufficient probability or data to make a JM prediction). FIG. 3 illustrates how the various sensor-specific classifiers complement each other under various motion situations (e.g., some JM situations and some separate motion situations). These various complementary results can be used by a unified JM classifier (e.g., state machine, voting algorithm, machine learning classifier, or equivalent) to make unified JM prediction based on the individual JM results, yielding an unprecedented coverage for identifying JM situations.

For example, in a scenario where two different UEs 101 are in different vehicles 103 that are near each other in a traffic jam, using location or GPS/GNSS data alone may result in a falsely classifying the two UEs 101 as being in joint motion (i.e., moving together in the same vehicle 103). This is because there relatively motion may appear to be relatively consistent because the two different vehicles 103 will be moving at approximately the same times and locations relative to each other because they will be stuck within the flow of the traffic jam. However, when other sensor data (e.g., accelerometer data) is considered (alone or in combination with the location data) for detecting joint motion according to the embodiments described herein, a more accurate detection can be obtained. For example, the high frequencies of the accelerometer data obtained from the two UEs 101 will likely differ because the magnetic fields in the two different vehicles 103 are likely to be substantially different.

In one embodiment, the unified JM predictions (e.g., JM data 111) can be transmitted over a communication network 115 as an output to a services platform 117 (e.g., supporting one or more services 119 a-119 k—also collectively referred to as services 119) and/or content providers 121 a-121 j (also collectively referred to as content providers 121) to provide one or more potential applications or services including but not limited to any of the following:

-   -   In paid rides (e.g. taxi fares), JM prediction can serve as a         positive identification that the ride took place and a trigger         to payment event, and in some embodiment, can also be used to         indicate falsely-cancelled rides to reduce or to prevent fraud;     -   For personal safety, JM prediction can be sued to verify that         passengers took the correct taxi/ride;     -   For group safety, JM prediction can be used to verify that in a         group ride (such as school bus or tourist bus), all individuals         are in the bus and no one is left behind;     -   For ride sharing recommendation, JM prediction can be used to         determine the identification of people sharing the same train,         and offer them to share a taxi/shared ride for the ‘last mile’         issue;     -   For taxi/shared rides, JM prediction can be used to determine         the exact location of a pickup and/or drop-off of a passenger;     -   For insurance, JM prediction enables insurance companies to         apply a ride-sharing insurance policy for a shared-ride when the         ride occurs and to apply a regular insurance policy when a         regular drive (i.e., non-ride-sharing trip) occurs for specific         driver with a dual use vehicle.

In one embodiment, the system 100 includes a JM platform 109 that is capable of performing one or more functions related to detecting JM based on multiple sensor data, according to one embodiment. As shown in FIG. 4, the JM platform 109 includes one or more components to perform the functions. In addition or alternatively, in one embodiment, one or more of the UEs 101 for which joint motion is being detected may include one or more equivalent components to perform the JM detection functions alone or in combination with the JM platform 109. It is contemplated that the functions of these components may be combined or performed by other components of equivalent functionality. In this embodiment, the JM platform 109 includes a data ingestion module 401, two or more sensor specific JM classifiers 403 a-403 n (also collectively referred to as JM classifiers 403), unified JM classifier 405, and output module 407. In one embodiment, the sensor specific JM classifiers 403 and/or the unified classifier 405 can be based on one or more machine learning models, other JM classification algorithms, and/or equivalent (e.g., decision trees, rules, etc.) to predict JM from corresponding sensor data 107 from associated with respective sensor types (e.g., location sensors, IMU sensors, BT sensors, NFC sensors, acoustic sensors, magnetometers, etc.) and/or map meta data (e.g., queried from the geographic database 113), according to the embodiments described herein. In one embodiment, the unified classifier 405 can be a state machine, voting algorithm, and/or equivalent that input the individual JM predictions of the sensor specific JM classifiers 403 to compute a unified JM prediction, according to the embodiments described herein. The above presented modules and components of the JM platform 109 can be implemented in hardware, firmware, software, or a combination thereof. Though depicted as a separate entity in FIG. 1, it is contemplated that the JM platform 109 may be implemented as a module of any other component of the system 100 (e.g., a component of a services platform 117, any of the services 119, UE 101, vehicle 103, etc. In another embodiment, one or more of the modules 401-407 may be implemented as a cloud-based service, local service, native application, or combination thereof. The functions of the JM platform 109 and the modules 401-407 are discussed with respect to FIGS. 5-8 below.

FIG. 5 is a flowchart of a process for detecting joint motion using multiple sensor data, according to one embodiment. In various embodiments, the JM platform 109 and/or any of the modules 401-407 of the JM platform 109 may perform one or more portions of the process 500 and may be implemented in, for instance, a chip set including a processor and a memory as shown in FIG. 17. As such, the JM platform 109 and/or the modules 401-407 can provide means for accomplishing various parts of the process 500, as well as means for accomplishing embodiments of other processes described herein in conjunction with other components of the system 100. Although the process 500 is illustrated and described as a sequence of steps, its contemplated that various embodiments of the process 500 may be performed in any order or combination and need not include all of the illustrated steps.

In step 501, the data ingestion module 401 retrieves sensor data at least two devices (e.g., UEs 101). The sensor data, for instance, is collected from the UEs 101 using at least one sensor type from among a plurality of sensor types available at the UEs 101. When determining joint motion between two or more people, each UE 101 corresponds to each person (e.g., each UE 101 is a personal device of the person). The UE 101, for instance, can be a mobile device equipped with an array of sensors of various types (e.g., location sensors, IMU sensors, BT sensors, NFC sensors, acoustic sensors, etc.). In other words, a sensor type refers to a sensor configured to measure or detect a different physical characteristic or parameter. In one embodiment, the joint motion platform 109 is configured with a different JM classifier, algorithm, etc. for generating a JM motion prediction from sensor data of a particular sensor type such that each sensor type of the plurality of sensor types (e.g., to be processed by the JM platform 109) is associated with a respective JM classifier 403.

In step 503, the respective JM classifier 403 processes the sensor data using the respective joint motion classifier for said each sensor type to compute a respective sensor-type joint motion prediction. In other words, the sensor data stream from each type of sensor of each of the UEs 101 is processed separately to make a joint motion prediction based only on the corresponding sensor data from a given sensor type to compute each sensor type joint motion prediction. These sensor-type joint motion predictions can also be referred to as individual joint motion predictions (i.e., individual to each sensor type). In one embodiment, the JM platform 109 can select a set of sensor types that are to be used to make a unified joint motion prediction on a systemwide basis or a case-by-case basis (e.g., depending on the capabilities or configuration of UEs 101 associated the people being evaluated for joint motion, on the availability of sensor data, availability of a JM classifier, etc.). Embodiments of the example sensor-specific or sensor type JM classifiers 403 are described below.

Location-Based JM classifier 403 a: In one embodiment, the plurality of different sensor types configured in the UEs 101 includes a location sensor type that collects location data (e.g., via location sensors such as GPS/GNSS, cellular based location, WiFi based location, etc.). By way of example, the Location-Based JM classifier 403 a operates as follows according to one embodiment:

-   -   (1) The Location-Based JM classifier 403 a assumes that the         uncertainty of the position estimation at each sample position         is known. If unknown, certain simplifying assumptions can be         made, such as assuming that all samples are derived from the         same distribution. This distribution is either known empirically         or modelled by a known distribution such as (but not limited to)         a normal distribution. Without loss of generality, the         embodiment described herein illustrates but is not limited to         the case where all samples are derived from the same normal         distribution.     -   (2) In a hypothesis-testing situation, the null hypothesis         corresponds to the two (or more devices) belonging to random         samples of a common normal distribution.

${f\left( {\left. x \middle| \mu \right.,\sigma^{2}} \right)} = {\frac{1}{\sqrt{2\pi\sigma^{2}}}{\exp\left\lbrack {- \frac{\left( {\overset{\rightarrow}{x} - \overset{\rightarrow}{\mu}} \right)^{2}}{2\sigma^{2}}} \right\rbrack}}$

-   -   (3) The resulting distances are positive-definite and belong to         a special case of the Chi Distribution, known as the Rayleigh         Distribution in 2D or Chi with three degrees of freedom for the         3D case. Each instantaneous probability at each time instance         t_(k) for JM depends on the distance d_(k).

${{P\left( d_{k} \right)} = {1 - {CD{F\left\lbrack {R{y\left( d_{k} \right)}} \right\rbrack}}}}{{Ry} = {\frac{\left( {\overset{\rightarrow}{x} - \overset{\rightarrow}{\mu}} \right)}{\sigma^{2}}{\exp\left( {- \frac{\left( {\overset{\rightarrow}{x} - \overset{\rightarrow}{\mu}} \right)^{2}}{2\sigma^{2}}} \right)}}}$

-   -   (4) By multiplying the k snapshots probabilities across a time         window, the Location-Based JM classifier 403 a gets a window         score from the rolling probability:

$P_{window} = \frac{\prod\limits_{k}P_{k}}{{\prod\limits_{k}P_{k}} + {\prod\limits_{k}\left( {1 - P_{k}} \right)}}$

FIGS. 6A-6D illustrates an example use case of using the Location-Based JM classifier 403 a for location-based JM prediction. The example use case illustrates a few points. Firstly, FIG. 6A illustrates a subplot 600 that depicts the distance that two UEs 101 are apart over a period of time (e.g., the y-axis indicates increasing distance from bottom to top, and the x-axis indicates increasing time from left to right). Location sensor data is used to determine the distance that the two UEs 101 are apart from each other. According to the FIG. 6A, the two UEs 101 met and separated eight times, with each “hill” in the subplot 600 corresponding to a period of separated motion.

The subplot 620 of FIG. 6B, subplot 640 of FIG. 6C, and subplot 660 of FIG. 6D highlight various aspects of the location-based JM prediction, according to one embodiment. For example, subplot 620 of FIG. 6B shows the instantaneous Rayleigh probability of whether the UEs 101 are in joint motion or separate. In this example, the probability of joint motion is on the y-axis and increases from bottom to top, and time is on the x-axis and increase from left to right. Subplot 620 shows some probability fluctuations resulting from instantaneous distance calculations and the noisy signal. Subplot 640 of FIG. 6C highlights the effect of the windowing method described above in smoothing the plot and providing a solution for the window. The example of subplot 640 is based on σ=20 m and T=60 s. The final subplot 660 of FIG. 6D indicates labelled events superimposed on the decision plot with a decision based on: P<0.1 indicating separate motion, P>0.9 indicating joint motion, and 0.1≤P≤0.9 indicating undecided motion. Darker lines correspond to separations and dashed lines to gatherings of the two UEs 101. In this example, the Location-Based JM classifier 403 a discovered all important JM/separate motion events within the first window of their occurrence.

In one embodiment, the Location-Based JM classifier 403 a can operate using partial location data. Partial location data, for instance, is location data that is computed using less than a number of independent data items for computing non-partial location data. For example, the location data in mobile device operating systems (e.g., Android OS) is determined, in general, by assimilation of data taken from various location data sources including but not limited to location satellites (e.g., GPS/GNSS satellites), cellular network (e.g., location of cellular towers/base stations/antennas and estimated distance), and WiFi network (e.g., location of stations and estimated distance). For these location methods, there generally is a minimum of concurrent and independent data items that is needed to estimate location. For example, data from at least four location satellites is required to determine latitude, longitude and elevation. However, to establish JM, fewer data items can be used, e.g., location satellites less than the minimum of four in case of obstruction due to urban environment. In this case, good correlation between the data transmitted by a single satellite, as received in two or more UEs 101 (e.g., smartphones) can be indicative to JM. Therefore, in one embodiment, the Location-Based JM classifier 403 a can use partial location data to make JM predictions.

IMU-Based JM Classifier 403 b: In one embodiment, the plurality of different sensor types configured in the UEs 101 includes IMU sensors. Since location provides only part of the picture, the embodiments described herein can utilizes IMU sensors in addition or as alternate to location sensors or other sensor types. Conceptually, the embodiments of the IMU-Based JM classifier 403 b are also applicable to any time-series based sensor that can be used in discovering cross-correlations between devices (e.g., barometric sensors, etc.). In one embodiment, a cross-correlation function can be used as a measure of similarity between two time series, acting as a function of the displacement of one function relative to the other. The function is also known as the sliding dot (inner) product.

By way of example, for discrete functions, the cross-correlation can be defined as (or equivalent):

${\left( {f*g} \right)\lbrack n\rbrack}\overset{def}{=}{\sum\limits_{m = {- \infty}}^{\infty}{{f^{*}\lbrack m\rbrack}{g\left\lbrack {m + n} \right\rbrack}}}$ where ƒ, g are two discrete functions, ƒ* is the complex conjugate of ƒ, and n refers to the lag between the two functions.

Two highly correlated time series (like those that would be expected to be seen in a JM situation) would result in a high global maximum correlation value, located very close to zero offset, at a small lag dt. The lag corresponds to the time difference between the two devices (differences in their time synchronization).

A separate motion scenario would yield a low value of maximum correlation score, with a highly varying lag factor. In one embodiment, for two uncorrelated time series, the maximum correlation is as small as the noise level and its position is random within the time window.

The IMU signals are typically noisy, due to their limited accuracy, but also due to undesired effects such as users utilizing their phones and causing movements unrelated to joint motion. Thus, in one embodiment, the raw IMU signals can be preprocessed to time-align the measurements from the two (or more) UEs 101, filter out high frequency noise and account for motion artifacts (due to user utilization), e.g., by incorporating gyroscope data with the accelerometer or equivalent.

In one embodiment, there are multiple ways in which one can construct feature vectors out of the IMU sensor data (e.g., feature vectors for machine classification). Features may include (but are not limited to) correlation data (e.g., maximum value, lag, decay rate, and/or the like) for each IMU sensor (e.g., accelerometer, gyroscope, magnetometer), amplitudes, measures of energy content in each sensor, entropy, spectral coherence, etc. The example of FIGS. 7A and 7B illustrate a simple model based only on accelerometer data, utilizing maximum correlation value and lag as features. The IMU-Based JM classifier 403 b calculates the correlation data in a sliding window of several seconds in duration (e.g., typically 8-10s). The correlation data from multiple windows (typically over a period of 30s to 200s) is used to get the averaged maximum cross-correlation and the spread of the time lag (e.g., standard deviation as a measure). JM is expected to have high correlation with narrow lag spread while separate motion will have low correlation with a wide lag spread. By way of example, there are multiple classifiers that the IMU-Based JM classifier 403 b can adopt for decision making such as but not limited to decision trees, logistic regression variants, SVM, neural networks, etc. For illustration purposes, FIGS. 7A and 7B demonstrate the results obtained using logistic regression classifier.

For example, empirical analysis can demonstrate about a 95% accuracy in 60 sec using the IMU-Based JM classifier 403 b as demonstrated in the histogram 700 of FIG. 7A and histogram 720 of FIG. 7B. Note, this approach does not require precise clock synchronization and works well with clock differences up to a few seconds or more.

In one embodiment, the IMU-Based JM classifier 403 b can also use the magnetic field, as typically sampled by the IMU, to determine or predict JM. There are a few utilization options possible. For example, the first one consists on the unique quasi-static magnetic field that is present within the car or vehicle 103, which is generated by the earth's magnetic field and the corresponding magnetic induction thereof. The spatial magnetic vector, as well as its relatively slow change over time due to turns, can be used for JM determination. In addition, higher frequency magnetic field components, emerging from the electronic systems of the car or vehicle 103, and which are typical to a vehicle model or even a single vehicle, can be used as a “vehicle fingerprint” to determine JM. For example, if both UEs 101 detect the same vehicle fingerprint, the IMU-Based JM classifier 403 b can determine joint motion.

NFC-Based JM Classifier 403 c: In one embodiment, the plurality of different sensor types configured in the UEs 101 includes NFC receivers or sensors. Generally, NFC communication works at extremely short ranges, typically up to 20 cm. In a JM situation, such short separations between two phones are plausible though not very frequent (e.g., if two UEs 101 are placed in the same compartment). If two UEs 101 can communicate via NFC, it is an absolute indication of proximity. If the proximity extends for more than a threshold time window (e.g., 1 min), it indicates a JM event that can be predicted by the NFC-Based JM Classifier 403 c.

Bluetooth-Based JM Classifier 403 d: In one embodiment, the plurality of different sensor types configured in the UEs 101 includes Bluetooth or equivalent short-range wireless receivers or sensors. Bluetooth signal intensity is distance-dependent and has a power-law decay as the distance increases. For example, the distance estimation model based on Bluetooth signals is given as: RSSI(d)=−(10×n)log₁₀ d−A Where n is the effective decay exponent, d is the relative distance between the communicating devices, and A is a reference received signal strength in dBm (e.g., the RSSI value measured when the separation distance between the receiver and the transmitter is one meter). Although the constants of the above expression are unknown, one can get a rough estimate based on the BT device spec, so if two UEs 101 can scan for the RSSI signal and get a meaningful value, the Bluetooth-Based JM classifier 403 d can determine that the two UEs 101 are nearby and can get a rough distance estimate to within a few meters. Moreover, if the RSSI is relatively constant over an extended period (e.g., more than a threshold duration), it is an indication of a JM event that can be used by the Bluetooth-Based JM classifier 403 d to predict JM.

In one embodiment, once the Bluetooth-Based JM classifier 403 d has an estimate of the distance between two or more UEs 101, a methodology similar to the location-based algorithm above can be applied to predict JM.

Acoustic-Based JM Classifier 403 e: In one embodiment, the plurality of different sensor types configured in the UEs 101 includes acoustic sensors (e.g., microphones). In one embodiment, acoustics can be employed in two modes of operation, active or passive. For example, in active mode, one of the two or more UEs 101 (or both) can broadcast short bursts of predefined signals via the internal speaker. The signals are arbitrary, but the system 100 can select signals in the higher part of the microphone frequency response, typically in the 15-22 kHz. Examples for such acoustic signals are pseudo random noise sequences (e.g., a maximum length sequences—MLS sequences) that allow for high signal to noise ratio at relatively low broadcast intensity, thus minimizing the audible inconvenience to the people around. The microphone on the receiving UE 101 records the signal and compares it to the (known) broadcast signal, e.g., by a time cross-correlation function. The Acoustic-Based JM classifier 403 e can use a high peak in the cross-correlation is an indication that two or more UEs 101 are in proximity of each other.

In the passive mode, the two UEs 101 synchronize the recording of background noise over a few seconds or other designated period of time. The two signals are highly correlated if the two devices are nearby. The Acoustic-Based JM classifier 403 e can then use the correlation to predict JM.

Map-Based Meta-Data JM Classifier 403 f: In one embodiment, combining maps (e.g., the geographic database 113) and location data (e.g., sensed by the UEs 101) can provide useful metadata. The Map-Based JM classifier 403 f can use the sensed location data of the UEs 101 to query for meta data or attributes associated with the location of the UEs 101 that can help increase the accuracy of JM predictions. For example, since drop-off and pickup of passengers are unlikely to happen on highways and tunnels, the JM events are detected at such locations are may likely be false positive events. In another use case, for specific individuals for which personal points of interest are known (e.g. home, work, etc.), or global points of interest such as shopping centers, train stations etc., there is an increased probability that JM events will take place at such locations. In other words, the Map-Based JM classifier 403 f, retrieves map data associated with one or more locations of the at least two UEs 101, and calculates a map-based joint motion prediction or verifies a joint motion prediction based on the map data. In one embodiment, instead of being used by a separate classifier, the map metadata can be fused in the unified classifier 405 described below.

In step 505, the unified classifier 405 processes the respective sensor-type joint motion prediction for said each sensor to compute a unified joint motion prediction for the at least two devices. As previously described, the unified joint motion prediction indicates that the at least two devices are sharing a same transportation vehicle based on multiple different sensor types and not just one sensor (e.g., as in the location data only approach). In one embodiment, considering that the JM platform 109 has multiple data sources (e.g., multiple individual sensor specific joint motion predictions) and metadata (e.g., map data from the geographic database 113) to fuse together, multiple approaches can be applied. The approaches include (but are not limited to) hidden Markov model, classifiers such as decision trees and their variants, auto-regressive linear models, deep neural networks (DNN), and/or equivalent.

In one embodiment, a State Machine architecture, comprised of current and all potential states of the system and transition functions between them, can also be constructed to compute a unified joint motion prediction from the different data sources. In yet another embodiment, the unified JM classifier 405 can be based on a voting algorithm or equivalent to combine the different sensor-specific joint motion predictions. One example voting scheme can include but is not limited to simply taking a majority vote among the different sensor-specific classifiers 403 to determine whether two or more UEs 101 are in joint motion, separate motion, and/or undecided motion.

In step 507, the output module 407 provides the unified joint motion prediction as an output. It is contemplated output can be used to support any service or application which relies or uses joint motion data. In one embodiment, the output can be used directly by the JM platform 109 or provided to external services or applications (e.g., via the service platform 117, services 119, content providers 121, etc.). FIG. 8 illustrates an example user interface 800 for presenting a unified joint motion prediction based on multiple sensor data, according to one embodiment. In the example of FIG. 8, the JM platform 109 has ingested sensor data from multiple sensors of two devices (e.g., device A and device B) to determine whether the two devices are in a joint motion state. The sensor data for instance includes data collected over a period of time (e.g., between 10:00 AM and 10:30 AM on a given day of the week). The JM platform 109 determines that the collected data includes the data of the following sensor types: location, IMU, IMU-magnetic, NFC, Bluetooth, acoustic, Barometer, and map metadata.

The JM platform 109 then generates a user interface element 801 that presents a list of sensor types available for predicting joint motion according and options for the user to select which of the sensor types to use for joint motion prediction. As shown, the user has selected the following sensor types (e.g., as indicated by a black box next to the sensor type): location, IMU, Bluetooth, acoustic, and map metadata. The JM platform 109 then applies the sensor specific classifiers 403 corresponding to the selected sensor types to make individual or sensor specific joint motion predictions. The unified classifier 405 of the JM platform 109 fuses individual joint motion predictions with the corresponding map metadata to make a unified joint motion prediction for the devices A and B for the corresponding time period. The JM platform 109 then presents a user interface element 803 to display the unified joint motion prediction (e.g., “Joint motion detected between device A and device B between 10:00 AM and 10:30 AM”) and provides the corresponding prediction probability or confidence (e.g., “Probability 0.95”).

In one embodiment, the JM platform 109 can provide the joint motion prediction as an output for use by other services, applications, components, etc. of system 100. For example, the joint motion prediction can be provided to the services platform 117 providing one or more services 119 such as but not limited to ride-sharing services, social networking services, mapping services (e.g., POI detection and/or classification). Examples of the use of joint motion predictions are described in more detail with respect to FIGS. 9-14 below.

FIG. 9 is a flowchart of a process for providing ride-sharing functions based on joint motion detected using multiple sensor data, according to one embodiment. In various embodiments, the services platform 117 and/or the any of the services 119 may perform one or more portions of the process 900 alone or in combination with the JM platform 109. The services platform 117 and/or any of the services 119 may be implemented in, for instance, a chip set including a processor and a memory as shown in FIG. 17. As such, the services platform 117, the services 119, and/or JM platform 109 can provide means for accomplishing various parts of the process 900, as well as means for accomplishing embodiments of other processes described herein in conjunction with other components of the system 100. Although the process 900 is illustrated and described as a sequence of steps, its contemplated that various embodiments of the process 900 may be performed in any order or combination and need not include all of the illustrated steps.

In step 901, the services platform 117 retrieves a joint motion prediction or detection indicating whether at least two devices are traveling in a same transportation vehicle. In one embodiment, the joint motion prediction is generated from mobile sensor data as described with respect to the embodiments of the process 500 of FIG. 5. For example, the joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types. In addition, each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction. As previously described, in one embodiment, the joint motion prediction regarding the two devices is used as a proxy to indicate to joint motion of respective users of the devices (e.g., predict that two or more users are traveling in the same vehicle 103 based on the sensor data collected from their phones and processed by the joint motion classifier(s) according to the embodiments described herein).

In step 903, the services platform 117 initiates or alters a ride-sharing function for the respective users of the at least two devices or other designated persons/entities (e.g., parents or relatives of children are the ride-sharing users) based on the joint motion prediction or detection. In another example, other designated persons/entities can include the ride-sharing vendor or provider to provide for notifications and/or further recommendations. As used herein, a ride-sharing function can be any task, operation, activity, etc. that is supported or provided by a ride-sharing/co-riding service including where at least two people are sharing a common vehicle (e.g., a car, train, bus, taxi, or any other mode of public or private transport). These at least two people, for instance, can be passengers and/or drivers/operators of the shared vehicle (e.g., vehicle 103). In addition, the ride-sharing/co-riding service can be a fee-based service (e.g., taxi, paid ride-sharing, public transport, transport service, etc.) or a non-fee based service (e.g., carpooling, shuttles, hitchhiking, etc.).

Steps 905-913 discussed below illustrate some, but not exclusive, examples of ride-sharing/co-riding functions that can be initiated based on the joint motion predictions computed by the JM platform 109. Any of the steps 905-913 can be performed alone or in combination with any other of the steps 905-913, and not all of the functions illustrated in the steps 905-913 need to be provided by a single or multiple services 119 of the services platform 117 or performed at the same time.

Step 905 is an example of a ride-sharing function used for paid or fee-based rides (e.g., taxi fares). In one embodiment, the services platform 117 can use a joint motion prediction (e.g., computed by the JM platform 109 according to the embodiments described herein and retrieved as described in step 901) between a user device (e.g., UE 101) associated with one or more passengers and a user device (e.g., UE 101) of associated with the driver or the vehicle 103 itself (e.g., when the vehicle 103 is an autonomous vehicle with no driver or operator). The joint motion prediction can indicate, for instance, when the passenger UE 101 and vehicle/driver UE 101 are in the same vehicle. In addition or alternatively, the joint motion prediction can be used to determine over what distances, routes, locations, etc. the passenger UE 101 and vehicle/driver UE 101 are in joint motion. Then, if the joint motion prediction coincides with a detected or predicted time and/or the detected or predicted distance/route/location/etc. of the trip, the services platform 117 can trigger a payment event from the passenger to the driver or ride-sharing service operator according to a configured fee agreement.

In one embodiment, it is contemplated that services platform 117 can use any time and/or distance margin/threshold to determine whether the joint motion prediction will trigger the payment event. For example, if the joint motion prediction occurs within a time window of the expected trip, the payment for the trip can be triggered. In another example, if the joint motion prediction occurs over a distance that covers at least a threshold proportion (e.g., greater than 25%) of the trip or route, the payment for the trip can be triggered. It is noted that the examples of payment triggering events or conditions are provided by way of illustration and not as limitations. In other embodiments, events other than payment events can be triggered based on the detected ride event. For example, instead of or in addition to triggering payment, the services platform 117 can use the joint motion prediction to set a status of the driver as occupied or not occupied based on whether the driver is in a joint motion state with a passenger.

In other words, the services platform 117 automatically detects that a ride event of a ride-sharing service has taken place between the respective users of the ride-sharing service based on the joint motion prediction, and then initiates a payment event based. FIG. 10A illustrates an example in which a passenger is riding a taxi with a driver. The JM platform 109 is monitoring the joint motion status of the passenger and driver by collecting sensor data from their respective UEs 101 according to the various embodiments described herein. For example, this monitoring can be started at the beginning of the trip or when the passenger requests a ride from the taxi driver. Then when the sensor data indicates that there is joint motion between the passenger and driver, the services platform 117 can use the joint motion prediction as an indication that the ride event has been detected. In one embodiment, the duration, extent, route, distance, etc. of the ride event or trip can be based on the duration, extent, etc. of the joint motion prediction. On completion of the ride event (e.g., detected based on the joint motion prediction indicating that the passenger and driver UEs 101 are no longer in a joint motion state), the services platform 117 automatically computes and initiates a payment event for the detected ride event. As shown in the FIG. 10A, a UE 101 of either the passenger or the driver can present a user interface 1001 that states that “A ride event between Passenger A and Driver B has been detected, and automatic payment has been initiated.”

In one embodiment, step 907 is an example of a ride-sharing function used for personal safety based on joint motion when ride-sharing or co-riding. For example, the services platform 117 can automatically detect that the respective users of the ride-sharing/co-riding service have taken the correct ride event. A correct ride event refers to a ride or trip between two passengers that have been previously booked or engaged by a passenger and assigned to a specific driver, vehicle, etc. of the ride-sharing service. In other words, the services platform 117 use the joint motion prediction determined from sensor data collected from the passenger and/or driver of ride-sharing service to determine whether the passenger has taken the correct or intended vehicle with the correct driver (e.g., gotten into the correct or intended taxi or ride-sharing vehicle ordered by the passenger). In some places, taking the wrong taxi, vehicle 103, etc. can be dangerous. Accordingly, this verification of correct ridership works both ways to protect the passenger and to protect the driver from using the incorrect vehicle.

In one embodiment, sensor data can be collected from both the passenger UE 101 and driver UE 101 at a time of the intended trip (e.g., indicated by a booking on the corresponding ride-sharing service). A joint motion prediction can be made between the passenger UE 101 and the driver UE 101, if there is no joint motion predicted between the passenger and driver during the time of the intended trip, then the services platform 117 can determine that either the passenger has taken a wrong taxi (e.g., if the passenger is detected to be in motion or on route), the driver has picked up the wrong passenger (e.g., if the driver is detected to be in motion or on route). If sensor data is also collected from the wrong driver or the wrong passenger, separate joint motion predictions between the original passenger and/or driver and the wrong passenger and/or driver can be computed to specifically identify which of the passenger and/or the driver has made the incorrect trip.

FIG. 10B illustrates an example use case in which a Passenger A has booked a trip with Taxi A but has incorrectly entered into Taxi B instead. In this example, sensor data is collected from the taxi fleet including both Taxis A and B as well as from Passenger A (e.g., collection of Passenger A sensor data initiated on booking of the trip). The services platform 117 can request a joint motion prediction between Passenger A and Taxi A (e.g., the intended taxi) at the expected start of the trip. If not, joint motion is detected between Passenger A and Taxi A is detected within a threshold time window of the anticipated start of the trip, the services platform 117 can request joint motion predictions for other nearby active taxis (e.g., Taxi B) and Passenger A. In this case, the services platform 117 determines that Taxi B is active within proximity of the pickup location of Passenger A and requests or retrieves a joint motion prediction between Passenger A and Taxi B. The joint motion prediction based on the sensor data according to the various embodiments described herein indicates that Passenger A and Taxi B (e.g., the wrong taxi) are in joint motion. Therefore, the services platform 117 determines that Passenger A has entered the wrong taxi or Taxi B has picked up the wrong passenger. In response, the services platform 117 initiate the presentation of a safety alert message on a UE 101 of the passenger and/or driver. For example, FIG. 10B illustrates a user interface 1011 presented on a UE 101 of a passenger to alert the passenger of the potential mistaken trip (e.g., “Safety Alert! We have detected that you have taken the wrong taxi.” In addition or alternatively, the services platform 117 can trigger an event to send an alternative ride to the passenger Taxi B if Taxi B alters it's planned trip to take Passenger A to her or his destination instead.

In one embodiment, step 909 is an example of a ride-sharing function used for group safety based on joint motion when ride-sharing or co-riding. For example, the JM platform 109 can collect sensor data from respective UEs 101 multiple users that are traveling or intending to travel as a single group. The JM platform 109 can then monitor the joint motion status of all or some of the members of the group with respect to each other. If the services platform 117 determines that the joint motion prediction from the JM platform 109 indicates that any one user in the group is no longer in joint motion with the others, then a group safety alert message can be presented via the UEs 101 of one or more of the group members or some other designated entity or authority.

For example, in a school bus/school trip use case, the services platform 117 can use the joint motion prediction for the children on the bus or trip to make sure that all children are grouped (e.g., either on the bus or off the bus), and provide a confirmation notice or a safety alert to a responsible authority (e.g., a teacher, chaperone, driver, etc.). FIG. 10C illustrates a user interface 1021 that indicates that “Child A is no longer in joint motion with the group” based on the group joint motion prediction. It is noted that the school bus/school trip use case is provided by way of illustration and not as a limitation. It is contemplated that group joint motion can be monitored in any use case where group travel occurs. For example, the embodiments of step 909 can be applied for tourist buses, for military troops and even for parents to make sure that kids are not forgotten in the car.

In one embodiment, step 911 is an example of a ride-sharing function used for providing ride-sharing recommendations. Take for instance two or more people that ride the same transportation vehicle (e.g., a train) and have roughly the same destination. The services platform 117 (e.g., a centralized system) can detect that they co-ride based on joint motion predictions and offer them a shared solution for the last mile problem. In one embodiment, the offer or recommendation is dynamic, no pre-planning is required, and it is based on identifying the co-ride event (e.g., traveled together) on the vehicle and the destination intent (e.g., determined explicitly or predicted). In other words, the services platform 117 can use the identification of people sharing the same vehicle (e.g., car, train, etc.) to recommend that at least some of those continue their journey together in another vehicle of a multi-leg journey to the same destination or destinations located within proximity of each other. This recommendation, for instance, can help solve the last mile problem where passengers using traditional public transport (e.g., trains) reach a public transport station near their destinations and then have to continue their trip from the station to their ultimate destination via another means of transport.

In one embodiment, the services platform 117 can retrieve joint motion predictions determined from sensor data collected from devices of users on the train. Then, for the users determined to be in joint motion on the train, the services platform 117 can determine (e.g., via set destinations, calendar entries, user input, and/or any other equivalent means) or predict (e.g., mobility patterns, travel histories, and/or any other equivalent means) the respective destinations of each of the users in joint motion on the train. The services platform 117 can then group the user based on the proximity of their respective locations, and recommend that users who are traveling to the same destination or to respective destinations within a proximity threshold share a vehicle 103 to reach that destination. In other words, the services platform 117 can use joint motion predictions to determine when users are using the same transportation vehicle for a first leg of a trip, and then recommend to at least some of the users on the first leg to continue a second leg of the trip together by sharing another transportation vehicle to a next or final destination.

FIG. 10D illustrates an example user interface 1031 for providing a ride-sharing recommendation according to the embodiments of step 911. In this example, a Passengers A, B, and C have been detected via a joint motion prediction (e.g., generated according to the embodiments described herein) to be traveling on the same train, and are headed to same destination (e.g., Point of Interest (POI) A) after the train ride. The services platform 117 can then generate a recommendation that all three Passengers A, B, and C share the same taxi to reach POI A after the train ride. The recommendation can then be presented to UEs 101 of one or more of the Passengers A-C. The user interface 1031 of FIG. 10D illustrates a user interface that is presented to Passenger A to recommend that the passenger share the a taxi to POI A stating: “Your Co-Passengers B and C are also headed to POI A, we recommend that you share a ride with them to reach POI A after your train ride.” In on embodiment, the user interface 1031 can also present an option 1033 to book the taxi together with the Passengers B and C.

In one embodiment, step 913 illustrates an example of a ride-sharing function for determining pick-up/drop-off locations based on joint motion. For example, the services platform 117 can use the joint motion prediction (e.g., generated using sensor data according to the embodiments described herein) corresponding to a ride-sharing/co-ride event to determine where the co-ride event started (e.g., the pick-up location) and where the co-ride event ended (e.g., the drop-off location). In one embodiment, the services platform 117 can determine the pick-up location as the location where the joint motion prediction indicates the passenger/user and driver/vehicle enter a joint motion state. Conversely, the drop-off location can be determined as where the joint motion prediction indicates that the passenger/user and driver/vehicle exit the joint motion state. The pick-up and/or drop-off locations determined by the services platform 117 can then be used to support other ride-sharing functions (e.g., trip verification, fee calculation, and/or the like).

In one embodiment, step 915 illustrates an example of a ride-sharing function for providing usage-based insurance of ride-sharing vehicles. The services platform 117, for instance, can automatically apply different insurance policies and/or rates to vehicles that have dual use a both a ride-sharing vehicle (e.g., taxi or equivalent) and non-ride sharing vehicle (e.g., personal use vehicle) based on their actual usage. For example, the services platform 117 can use the joint motion predictions of the JM platform 109 to determine when the vehicle is engaged in a ride-sharing event and then apply the corresponding ride-sharing insurance policy, terms, rates, etc. and when the vehicle is engaged in a personal drive event and then apply the corresponding personal insurance policy, terms, rates, etc.

In one embodiment, the services platform 117 determines whether the vehicle is engaged in a ride-sharing/co-ride event (e.g., operating in a shared ride mode) based on the joint motion prediction indicating that the driver is in a joint motion state with a ride-sharing service passenger during a trip in the vehicle. If the driver is determined to be in joint motion with a non-ride-sharing service passenger and/or a not in joint motion with any passenger, then the services platform 117 can determine that the vehicle is not engaged in a ride-sharing/co-ride event (e.g., operating in a personal mode). By way of example, in a shared ride mode, different insurance rates, policies, etc. can be applied (e.g., rates higher than personal rates). In this way, the services platform 117 enables insurance companies to insure a shared ride only when it occurs, and to apply regular or personal insurance rates and conditions when a regular or personal drive occurs for a specific driver.

FIG. 10D illustrates an example user interface 1041 for applying insurance based on ride-sharing usage. In this example, a driver uses a vehicle for both providing a commercial ride-sharing service as well as for personal use. In addition, the driver is currently carrying a ride-sharing customer, and the JM platform 109 is monitoring the sensor data collected from both the customer and driver to compute a joint motion prediction according to the various embodiments described herein. The joint motion prediction indicates that the driver is joint motion with the ride-sharing customer in the same vehicle. Accordingly, the services platform 117 applies the applicable ride-sharing insurance policy and can present a message in the user interface 1041 to indicate that “Shared Ride Mode Detected, Ride-Sharing Insurance Policy is now Activated for this Trip.”

In one embodiment, step 917 is an example of a ride-sharing function used to detect fraudulent or abusive ride-sharing activity. For example, many ride-sharing companies experience unjustified or fraudulent cancellation events by drivers for some trips. A cancellation event is a request by either the passenger or driver to cancel a booked or scheduled trip. In some cases, these are fraudulent cancellation events in which the driver does take the passenger and then earns both the cancellation fee and the ride fee. To guard against these cases, the services platform 117 can use the joint motion prediction computed according to the various embodiments described herein to determine that a cancellation event for a trip by the driver/vehicle is fraudulent. For example, if the retrieved joint motion prediction for a passenger and driver indicates that they were in a joint motion state during a trip for which a cancellation event or request has been initiated, the services platform 117 can classify the cancellation event as fraudulent or potentially fraudulent. In one embodiment, the services platform 117 can initiate a display of the classification to a service agent, the driver, passenger, and/or the like. FIG. 10E illustrates an example fraud detection message in a user interface 1051 stating that “Trip Cancellation is Potentially Invalid Based on Detected Joint Motion Between Passenger and Driver During a Trip for Which the Cancellation Request was Received” with an option 1053 to “Call Customer Service” to discuss or confirm the request.

FIG. 11 is a flowchart of a process for providing social networking functions based on joint motion detected using multiple sensor data, according to one embodiment. In various embodiments, the services platform 117 and/or the any of the services 119 may perform one or more portions of the process 1100 alone or in combination with the JM platform 109. The services platform 117 and/or any of the services 119 may be implemented in, for instance, a chip set including a processor and a memory as shown in FIG. 17. As such, the services platform 117, the services 119, and/or JM platform 109 can provide means for accomplishing various parts of the process 1100, as well as means for accomplishing embodiments of other processes described herein in conjunction with other components of the system 100. Although the process 1100 is illustrated and described as a sequence of steps, it is contemplated that various embodiments of the process 1100 may be performed in any order or combination and need not include all of the illustrated steps.

In step 1101, the services platform 117 determines a co-ride event between at least two users based on a joint motion prediction computed using sensor data collected from respective devices associated with the at least two users. A co-ride event, for instance, refers to the users traveling the same transportation vehicle. As discussed above, the users can include any combination of one or more passengers, the vehicle in which the passengers are riding, and a driver of the vehicle (e.g., no driver may be present when the vehicle is an autonomous vehicle). In one embodiment, the joint motion prediction is computed based on sensor data collected from the respective devices using at least one sensor type from among a plurality of sensor types according to the embodiments described herein. For example, each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction as a unified prediction of each sensor-type prediction. If the joint motion prediction for the two users of interest indicate that they are in a state of joint motion, then the services platform 117 can determine that the two or more users are engaged in a co-ride event (e.g., sharing or riding in the same vehicle).

In step 1103, the services platform 117 determines a latent social network between the at least two users based on the detected co-ride event. In one embodiment, the latent social network indicates an inferred social networking relationship between the at least two users. The latent social network can also indicate a new connection, a hidden connection, or a combination thereof between the at least two users. In other words, the latent social networking relationship between users is determined based on their mobility (e.g., the co-ride event) as opposed to determining the relationship from existing social networking services. For example, the services platform 117 can determine that there is a latent social network or relationship between two users if those two users have engaged in more than a threshold number of co-ride events (e.g., a threshold of any number of co-ride events greater than one event).

In step 1105, the services platform 117 provides the latent social network or mobility-inferred relationships among users as an output. In other words, the services platform 117 can use co-ride events to assess a latent social network. In one embodiment, once such a network is in place and provided as an output, the services platform 117 can use various social network analytical approaches or algorithms to further classify the latent social network, user relationships, network members, etc. This classification can also be combined with other user data or characteristics (e.g., based on various signals such as the places the users have visited, data available from other social networking services, user profile information, etc.) to further refine the classifications and/or to provide additional latent social networking services as described in the examples of steps 1107-1113 below. Any of the steps 1107-1113 can be performed alone or in combination with any of the other steps 1107-1113.

In step 1107, the services platform 117 classifies the users who are members of the determined latent social network as an “influencer” (e.g., a person with followers or subscribers in a social networking service) or an “influencee” (e.g., a person following or subscribing to the influencer) based, for instance, on one or more characteristics of the at least two users. For example, the services platform 117 can query publicly available data (e.g., existing social networking services, web pages, publications database, etc.) to determine whether any of the users are known influencers or influencees in various fields. For example, a user can be classified as an influencer if the user has more than a threshold number of subscribers or followers in another social networking service, video service, podcast service, any other media service, and/or the like. Conversely, a user can be classified as an influencee if the service platform 114 determines that the user subscribes to or follows the influencer in another service. It is noted that the examples described above for identifying influencers and influencees are provided by way of illustration and not as limitations.

In one embodiment, the classification can be further refined based on the places visited by the user in the co-ride event. The services platform 117, for instance, can determine the fields or categories associated with the places visited and then classify the influencers/influencees with respect to the that determined fields. For example, if the places visited include mostly shopping locations in a fashion district, the services platform 117 can designate the field as fashion. The services platform 117 then determines the influencer/influencee classification with respect to fashion (e.g., does the influencer publish and have followers in the fashion field, or does the influencee follow fashion topics).

In one embodiment, once the users or members of the latent social network are classified as influencers or influencees, the services platform 117 can use the classifications to various such cases such as but not limited to sales promotions/recommendations. FIG. 12A illustrates an example user interface 1201 presented on a UE 101 of a detected influencee with a latent social networking relationship to an influencer in a co-ride event. In this example, the user interface 1201 is a recommendation presented to the influencee on behalf of the influencee stating “You are currently riding with Influencer A who recommends the sale going on at Shop A near your destination.”

In step 1109, the services platform 117 recommends a collaboration activity between the at least two users, one or more other users (other members of the latent social network such as friends of friends), or a combination thereof based on the latent social network. The collaboration event includes a ride-sharing event. In other words, by analyzing the latent social network, the services platform 117 can help various unconnected parties to collaborate and/or take rides together. For example, as illustrated in the example user interface 1211 of FIG. 12B, if the latent social network indicates that two previously unconnected people have been on the same train together for more than a threshold number of times, the services platform 117 can recommend that the two users share a taxi to the next destination. User interface 1211 illustrates an example of such a recommendation which states “You have shared the same train with Passenger A more than 5 times, would you like to share a taxi to the next destination with Passenger A?”

In step 1111, the services platform 117 determines a relationship type between the at least two users in the latent social network based on a location associated with the joint motion prediction. In other words, the services platform 117 can analyze the types of locations and/or other contextual information to classify the type of latent social networking relationship between two or more users (e.g., co-workers, friends going out, gym friends, parents taking children to/from events). For example, if a location (e.g., origin, destination, waypoint, etc.) associated with the co-ride event used to infer the latent social network is a work location occurring on a configured work schedule, the relationship between the co-riding users can be classified as “co-workers.” Similarly, if the location associated with the co-ride event is a restaurant/theater/bar/etc. occurring in the evenings or weekends, the relationship between the co-riding users can be classified as “friends going out.” It is contemplated that the services platform 117 can use any criteria to classify the relationships based on location and/or other contextual parameters (e.g., time, activity, etc.) associated with the co-ride event.

In step 1113, the services platform 117 determines an identity of at least one of the at least two users based on the latent social network. In one embodiment, the services platform 117 can compare already known connections (e.g., from other social network services) to determine the identity of one or more of the users in the latent social network derived from the co-ride event. If one user or member of the latent social network relationship is known but the other user is not, the services platform 117 can query another social networking containing previously known connections or relationships to determine a likely identify match for the unknown user in the latent social network. For example, if Friend A and Friend B are detected in a co-ride event and the services platform 117 has access to only the identity of the Friend A. The services platform 117 can query another social network or other database of known connections to determine a person who may match Friend A, then the service platform 117 can identify unknown Friend A using the identity of the retrieved known connection. If no identity is or can be determined, the services platform 117 can use a placeholder identity of the unknown Fried A to track the relationship. In this way, unofficial (e.g., not known in any available database or service) or hidden (e.g., not previously shared or disclosed by the users) connections or relationships between people can be inferred based on co-ride events.

FIG. 13 is a flowchart of a process for providing point of interest (POI) detection and/or classification using joint motion, according to one embodiment. In various embodiments, the services platform 117 and/or the any of the services 119 may perform one or more portions of the process 1300 alone or in combination with the JM platform 109. The services platform 117 and/or any of the services 119 may be implemented in, for instance, a chip set including a processor and a memory as shown in FIG. 17. As such, the services platform 117, the services 119, and/or JM platform 109 can provide means for accomplishing various parts of the process 1300, as well as means for accomplishing embodiments of other processes described herein in conjunction with other components of the system 100. Although the process 1300 is illustrated and described as a sequence of steps, its contemplated that various embodiments of the process 1300 may be performed in any order or combination and need not include all of the illustrated steps.

In one embodiment, the process 1300 can be used for POI or other user location classification and detection to improve or provide classifications of POIs by having the additional insights of co-ride data. Using co-ride data (e.g., determined from joint motion), the services platform 117 (e.g., a mapping service) can understand people's POIs and their corresponding labels. The POI classification and detection can be general if the classification/detection is based on joint motion data collected from a group of users, and/or personalized to one or more users if joint motion data is collected from individual users over multiple instances. For example in a personalized POI classification and detection use case, if two people ride in the same vehicle every workday at 8 am to a place and ride back at 5 pm, the services platform 117 can classify that they are co-workers who work at the location they travel to, and that they probably live in proximity to the place they return to. Although traditional approaches may also classify a potential location as a work place, the co-ride data used according to embodiments provided here provide additional data to increase the confidence of the predicted classification (e.g., classifying the location as a work place because co-workers co-ride to that location at typical working hours). In another example use case, similar classifications can be made for the actual users or people. For example, if it is a weekend and the services platform 117 detects people constantly sharing rides, they are probably “going-out friends”. In a similar manner, the services platform 117 can identify gym-friends, soccer dads/moms, etc. by combining co-ride data with other contextual data (e.g., time, location, activity, etc.) to increase the confidence of the classification over using the contextual data alone.

Accordingly, in step 1301, the services platform 117 determines co-ride data for at least two users based on a joint motion prediction computed using sensor data collected from respective devices associated with the at least two users. In one embodiment, the joint motion prediction is computed based on sensor data collected from the respective devices using at least one sensor type from among a plurality of sensor types according to the embodiments described herein. Each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction.

In step 1303, the services platform 117 processes the co-ride data to perform a detection, a classification, or a combination thereof of one or more locations associated with the joint motion prediction. In one embodiment, the joint motion prediction indicates that the at least two users are traveling in a same transportation vehicle, and the one or more locations are an origin, a destination, a waypoint, or a combination thereof of a trip taken by the vehicle which the users are riding. The services platform 117 can use criteria such as but not limited to the number of observed co-ride events repeatedly involving the same locations. For example, the services platform 117 can detect and classify these locations as locations of interest to the users if there are more than a threshold number of trips involving the locations. In the example of the users traveling back and forth to work above, the service platform 117 can monitor co-ride events taken by the users and then if there are more than the threshold number, the locations associated with the co-ride event can be detected and classified. The locations, for instance, be determined from as the beginning and/or ending locations of the joint motion state between the users. In one embodiment, waypoints can also be detected by stopping locations (e.g., based on speed data or other sensed data from the users' devices).

In one embodiment, the detected locations can be simply classified or labeled as locations of interest of the users. In other embodiments, the services platform 117 can perform additional classification to further label the locations. For example, in step 1305, the classification comprises classifying the one or more locations as a POI. In one embodiment, the POIs can be personal to the co-riding users or can be POIs that have general interest to all map service users. For example, if the same personal locations of interest are repeatedly of detected for multiple groups of co-riding users, then the service platform 117 can classify the locations as potential new POIs that can be included in future map updates.

In yet another embodiment, the services platform 117 can use contextual information or patterns of contextual information about the co-riding data or events to further classify the detected locations. In particular, the services platform 117 can determine a contextual parameter associated with the trip, and the classification of the one or more locations can be further based on the contextual parameter. By way of example, the contextual parameter includes a temporal parameter indicating a time of day, a day of a week, a month, a season, or a combination thereof of the co-riding events recorded in the co-riding data. The context can be used to determine a pattern associated with the users' co-riding events. As described in the example above, co-rides between two locations that start at a typical workday (e.g., 8 am) and then return from the location at the end of a typical workday (e.g., 5 pm) can be used to classify the destination location of the 8 am co-ride event and the origin location of the 5 pm co-ride event as a potential work location. Similarly, the starting location of the 8 am co-ride event and the destination location of the 5 pm co-ride event can be classified as a potential home location. FIG. 14A illustrates an example user interface 1401 that can be presented on a UE 101 to display a detected and classified work location. As shown, the user interface 1401, the services platform initiates or provides data for displaying a message indicating “You have had 5 co-rides to Location A at 8 am and 5 return co-rides from Location A at 5 pm” and prompts the user to indicate whether to “Set Location A as your work location”. The user can response yes or no via option boxes 1403

In one embodiment, in addition to or instead of classifying the locations, the services platform 117 can classify one or more characteristics of the users. For example, in step 1307, the services platform determines a user classification of the at least two users based on the classification of the one or more locations. In other words, depending on the determined classification of the locations and/or contextual information about the users' co-riding data (e.g., time, activity, etc.), the services platform 113 can infer the classifications of the users themselves. Following on the example above, if the services platform 117 has classified a work location using the co-ride data, the services platform 113 can also classify the participating users of the co-rides to and/or from the work location as potential “co-workers” or any other category that has been associated with the classified location (e.g., that also represent the classified characteristics of the users). This is because, for instance, it can be likely that two users who travel to and from work together repeatedly may be co-workers. FIG. 14B continues the example of FIG. 14A in which a work location has been detected and illustrates a user interface 1401 for presenting user classifications indicating one or more characteristics of the users (e.g., characteristic indicating co-worker status). The services platform 113 then also classifies the co-riding users as potential co-workers, and initiates or provides data for displaying the user interface 1411 indicating “You have had 5 co-rides with User A to your work location” and ask whether to “Set User A as your co-worker.” The user interface 1411 provides options boxes 1413 for the user to respond.

It is noted that the examples of classifying locations as a work location and co-riding users as co-workers are provided by way of illustration and not as limitation. It is contemplated that the services platform 117 can use any location and/or user classifications according to the embodiments describe herein. For example, if the location of interest is classified as a gym, the co-riding users can be classified as “gym buddies.” Similarly, if the location of interest is a school, and contextual information indicate a morning drop-off and early afternoon pickup on weekdays, the co-riding users can be classified as “parent and child.”

In step 1309, the services platform 117 provides the detection, the classification, or a combination thereof as an output. The services platform 117, for instance, can store the point of interest, the classification the point of interest, the classification of the users, or a combination thereof in a geographic database (e.g., the geographic database 113) for access by end users. In one embodiment, the point of interest can also be personalized to one or more of the at least two users so that the detected locations and/or the labels/classifications are presented only to the applicable users.

Returning to FIG. 1, the system 100 comprises one or more UEs 101 and/or one or more vehicles 103 having connectivity to the JM platform 109 via a communication network 115. By way of example, the UEs 101 may be a personal navigation device (“PND”), a cellular telephone, a mobile phone, a personal digital assistant (“PDA”), a watch, a camera, a computer, an in-vehicle or embedded navigation system, and/or other device that is configured with multiple sensors types that can be used for join motion detection according to the embodiments described herein. It is contemplated, that the cellular telephone or other wireless communication device may be interfaced with an on-board navigation system of an autonomous vehicle or physically connected to the vehicle 103 for serving as the navigation system. Also, the UEs 101 and/or vehicles 103 may be configured to access the communication network 115 by way of any known or still developing communication protocols. Via this communication network 115, the UEs 101 and/or vehicles 103 may transmit sensor data collected from multiple different sensor types 105 for facilitating joint motion detection.

The UEs 101 and/or vehicles 103 may be configured with multiple sensors 105 of different types for acquiring and/or generating sensor data according to the embodiments described herein. For example, sensors 105 may be used as GPS or other positioning receivers for interacting with one or more location satellites to determine and track the current speed, position and location of a vehicle travelling along a roadway. In addition, the sensors 105 may gather IMU data, NFC data, Bluetooth data, acoustic data, barometric data, tilt data (e.g., a degree of incline or decline of the vehicle during travel), motion data, light data, sound data, image data, weather data, temporal data and other data associated with the vehicle and/or UEs 101 thereof. Still further, the sensors 105 may detect local or transient network and/or wireless signals, such as those transmitted by nearby devices during navigation of a vehicle along a roadway. This may include, for example, network routers configured within a premise (e.g., home or business), another UE 101 or vehicle 103 or a communicable traffic system (e.g., traffic lights, traffic cameras, traffic signals, digital signage). In one embodiment, the JM platform 109 aggregates multiple sensor data gathered and/or generated by the UEs 101 and/or vehicles 103 resulting from traveling in joint motion or separate motion.

By way of example, the JM platform 109 may be implemented as a cloud-based service, hosted solution or the like for performing the above described functions. Alternatively, the JM platform 109 may be directly integrated for processing data generated and/or provided by the service platform 117, one or more services 119, and/or content providers 121. Per this integration, the JM platform 109 may perform client-side state computation of road curvature data.

By way of example, the communication network 115 of system 100 includes one or more networks such as a data network, a wireless network, a telephony network, or any combination thereof. It is contemplated that the data network may be any local area network (LAN), metropolitan area network (MAN), wide area network (WAN), a public data network (e.g., the Internet), short range wireless network, or any other suitable packet-switched network, such as a commercially owned, proprietary packet-switched network, e.g., a proprietary cable or fiber-optic network, and the like, or any combination thereof. In addition, the wireless network may be, for example, a cellular network and may employ various technologies including enhanced data rates for global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS), etc., as well as any other suitable wireless medium, e.g., worldwide interoperability for microwave access (WiMAX), Long Term Evolution (LTE) networks, code division multiple access (CDMA), wideband code division multiple access (WCDMA), wireless fidelity (WiFi), wireless LAN (WLAN), Bluetooth®, Internet Protocol (IP) data casting, satellite, mobile ad-hoc network (MANET), and the like, or any combination thereof.

A UE 101 is any type of mobile terminal, fixed terminal, or portable terminal including a mobile handset, station, unit, device, multimedia computer, multimedia tablet, Internet node, communicator, desktop computer, laptop computer, notebook computer, netbook computer, tablet computer, personal communication system (PCS) device, personal navigation device, personal digital assistants (PDAs), audio/video player, digital camera/camcorder, positioning device, television receiver, radio broadcast receiver, electronic book device, game device, or any combination thereof, including the accessories and peripherals of these devices, or any combination thereof. It is also contemplated that a UE 101 can support any type of interface to the user (such as “wearable” circuitry, etc.).

By way of example, the UE 101 s, the JM platform 109, the service platform 117, and the content providers 121 communicate with each other and other components of the communication network 115 using well known, new or still developing protocols. In this context, a protocol includes a set of rules defining how the network nodes within the communication network 115 interact with each other based on information sent over the communication links. The protocols are effective at different layers of operation within each node, from generating and receiving physical signals of various types, to selecting a link for transferring those signals, to the format of information indicated by those signals, to identifying which software application executing on a computer system sends or receives the information. The conceptually different layers of protocols for exchanging information over a network are described in the Open Systems Interconnection (OSI) Reference Model.

Communications between the network nodes are typically effected by exchanging discrete packets of data. Each packet typically comprises (1) header information associated with a particular protocol, and (2) payload information that follows the header information and contains information that may be processed independently of that particular protocol. In some protocols, the packet includes (3) trailer information following the payload and indicating the end of the payload information. The header includes information such as the source of the packet, its destination, the length of the payload, and other properties used by the protocol. Often, the data in the payload for the particular protocol includes a header and payload for a different protocol associated with a different, higher layer of the OSI Reference Model. The header for a particular protocol typically indicates a type for the next protocol contained in its payload. The higher layer protocol is said to be encapsulated in the lower layer protocol. The headers included in a packet traversing multiple heterogeneous networks, such as the Internet, typically include a physical (layer 1) header, a data-link (layer 2) header, an internetwork (layer 3) header and a transport (layer 4) header, and various application (layer 5, layer 6 and layer 7) headers as defined by the OSI Reference Model.

FIG. 15 is a diagram of a geographic database, according to one embodiment. In one embodiment, the geographic database 113 includes geographic data 1501 used for (or configured to be compiled to be used for) mapping and/or navigation-related services, such as for providing map embedding analytics according to the embodiments described herein. For example, the map data records stored herein can be used to determine the semantic relationships among the map features, attributes, categories, etc. represented in the geographic data 1501. In one embodiment, the geographic database 113 include high definition (HD) mapping data that provide centimeter-level or better accuracy of map features. For example, the geographic database 113 can be based on Light Detection and Ranging (LiDAR) or equivalent technology to collect billions of 3D points and model road surfaces and other map features down to the number lanes and their widths. In one embodiment, the HD mapping data (e.g., HD data records 1511) capture and store details such as the slope and curvature of the road, lane markings, roadside objects such as sign posts, including what the signage denotes. By way of example, the HD mapping data enable highly automated vehicles to precisely localize themselves on the road.

In one embodiment, geographic features (e.g., two-dimensional or three-dimensional features) are represented using polylines and/or polygons (e.g., two-dimensional features) or polygon extrusions (e.g., three-dimensional features). In one embodiment, these polylines/polygons can also represent ground truth or reference features or objects (e.g., signs, road markings, lane lines, landmarks, etc.) used for visual odometry. For example, the polylines or polygons can correspond to the boundaries or edges of the respective geographic features. In the case of a building, a two-dimensional polygon can be used to represent a footprint of the building, and a three-dimensional polygon extrusion can be used to represent the three-dimensional surfaces of the building. Accordingly, the terms polygons and polygon extrusions as used herein can be used interchangeably.

In one embodiment, the following terminology applies to the representation of geographic features in the geographic database 113.

“Node”—A point that terminates a link.

“Line segment”—A straight line connecting two points.

“Link” (or “edge”)—A contiguous, non-branching string of one or more line segments terminating in a node at each end.

“Shape point”—A point along a link between two nodes (e.g., used to alter a shape of the link without defining new nodes).

“Oriented link”—A link that has a starting node (referred to as the “reference node”) and an ending node (referred to as the “non reference node”).

“Simple polygon”—An interior area of an outer boundary formed by a string of oriented links that begins and ends in one node. In one embodiment, a simple polygon does not cross itself.

“Polygon”—An area bounded by an outer boundary and none or at least one interior boundary (e.g., a hole or island). In one embodiment, a polygon is constructed from one outer simple polygon and none or at least one inner simple polygon. A polygon is simple if it just consists of one simple polygon, or complex if it has at least one inner simple polygon.

In one embodiment, the geographic database 113 follows certain conventions. For example, links do not cross themselves and do not cross each other except at a node. Also, there are no duplicated shape points, nodes, or links. Two links that connect each other have a common node. In the geographic database 113, overlapping geographic features are represented by overlapping polygons. When polygons overlap, the boundary of one polygon crosses the boundary of the other polygon. In the geographic database 113, the location at which the boundary of one polygon intersects they boundary of another polygon is represented by a node. In one embodiment, a node may be used to represent other locations along the boundary of a polygon than a location at which the boundary of the polygon intersects the boundary of another polygon. In one embodiment, a shape point is not used to represent a point at which the boundary of a polygon intersects the boundary of another polygon.

As shown, the geographic database 113 includes node data records 1503, road segment or link data records 1505, POI data records 1507, joint motion data records 1509, HD mapping data records 1511, and indexes 1513, for example. More, fewer or different data records can be provided. In one embodiment, additional data records (not shown) can include cartographic (“carto”) data records, routing data, and maneuver data. In one embodiment, the indexes 1513 may improve the speed of data retrieval operations in the geographic database 113. In one embodiment, the indexes 1513 may be used to quickly locate data without having to search every row in the geographic database 113 every time it is accessed. For example, in one embodiment, the indexes 1513 can be a spatial index of the polygon points associated with stored feature polygons.

In exemplary embodiments, the road segment data records 1505 are links or segments representing roads, streets, or paths, as can be used in the calculated route or recorded route information for determination of one or more personalized routes. The node data records 1503 are end points corresponding to the respective links or segments of the road segment data records 1505. The road link data records 1505 and the node data records 1503 represent a road network, such as used by vehicles, cars, and/or other entities. Alternatively, the geographic database 113 can contain path segment and node data records or other data that represent pedestrian paths or areas in addition to or instead of the vehicle road record data, for example. In one embodiment, the nodes and links can make up the base map and that base map can be associated with an HD layer including more detailed information, like lane level details for each road segment or link and how those lanes connect via intersections. Furthermore, another layer may also be provided, such as an HD live map, where road objects are provided in detail in regard to positioning, which can be used for localization. The HD layers can be arranged in a tile format.

The road/link segments and nodes can be associated with attributes, such as geographic coordinates, street names, address ranges, speed limits, turn restrictions at intersections, and other navigation related attributes, as well as POIs, such as gasoline stations, hotels, restaurants, museums, stadiums, offices, automobile dealerships, auto repair shops, buildings, stores, parks, etc. The geographic database 113 can include data about the POIs and their respective locations in the POI data records 1507. The geographic database 113 can also include data about places, such as cities, towns, or other communities, and other geographic features, such as bodies of water, mountain ranges, etc. Such place or feature data can be part of the POI data records 1507 or can be associated with POIs or POI data records 1507 (such as a data point used for displaying or representing a position of a city).

In one embodiment, the geographic database 113 can also include joint motion data records 1509 for storing joint motion data predicted from one or more people or devices. The joint motion data records 1509 can also store related data including but not limited to underlying sensor data probe data, individual or sensor specific joint motion detections, available sensor types, and/or any other data used or generated according to the embodiments described herein. By way of example, the joint motion data records 1509 can be associated with one or more of the node records 1503, road segment records 1505, and/or POI data records 1507 to associate the detected joint motion with specific geographic areas or features. In this way, the map embedding data records 1509 can also be associated with the characteristics or metadata of the corresponding records 1503, 1505, and/or 1507.

In one embodiment, as discussed above, the HD mapping data records 1511 model road surfaces and other map features to centimeter-level or better accuracy (e.g., including centimeter-level accuracy for ground truth objects used for visual odometry based on polyline homogeneity according to the embodiments described herein). The HD mapping data records 1511 also include ground truth object models that provide the precise object geometry with polylines or polygonal boundaries, as well as rich attributes of the models. These rich attributes include, but are not limited to, object type, object location, lane traversal information, lane types, lane marking types, lane level speed limit information, and/or the like. In one embodiment, the HD mapping data records 1511 are divided into spatial partitions of varying sizes to provide HD mapping data to end user devices with near real-time speed without overloading the available resources of the devices (e.g., computational, memory, bandwidth, etc. resources).

In one embodiment, the HD mapping data records 1511 are created from high-resolution 3D mesh or point-cloud data generated, for instance, from LiDAR-equipped vehicles. The 3D mesh or point-cloud data are processed to create 3D representations of a street or geographic environment at centimeter-level accuracy for storage in the HD mapping data records 1511.

In one embodiment, the HD mapping data records 1511 also include real-time sensor data collected from probe vehicles in the field. The real-time sensor data, for instance, integrates real-time traffic information, weather, and road conditions (e.g., potholes, road friction, road wear, etc.) with highly detailed 3D representations of street and geographic features to provide precise real-time data (e.g., including probe trajectories) also at centimeter-level accuracy. Other sensor data can include vehicle telemetry or operational data such as windshield wiper activation state, braking state, steering angle, accelerator position, and/or the like. The HD mapping data records may be provided as a separate map layer.

In one embodiment, the geographic database 113 can be maintained by the content provider 121 in association with the services platform 117 (e.g., a map developer). The map developer can collect geographic data to generate and enhance the geographic database 113. There can be different ways used by the map developer to collect data. These ways can include obtaining data from other sources, such as municipalities or respective geographic authorities. In addition, the map developer can employ field personnel to travel by vehicle along roads throughout the geographic region to observe features and/or record information about them, for example. Also, remote sensing, such as aerial or satellite photography, can be used.

The geographic database 113 can be a master geographic database stored in a format that facilitates updating, maintenance, and development. For example, the master geographic database or data in the master geographic database can be in an Oracle spatial format or other spatial format, such as for development or production purposes. The Oracle spatial format or development/production database can be compiled into a delivery format, such as a geographic data files (GDF) format. Other formats including tile structures for different map layers may be used for different delivery techniques. The data in the production and/or delivery formats can be compiled or further compiled to form geographic database products or databases, which can be used in end user navigation devices or systems.

For example, geographic data is compiled (such as into a platform specification format (PSF)) to organize and/or configure the data for performing navigation-related functions and/or services, such as route calculation, route guidance, map display, speed calculation, distance and travel time functions, and other functions, by a navigation device, such as by a vehicle 103 and/or UE 101. The navigation-related functions can correspond to vehicle navigation, pedestrian navigation, or other types of navigation. The compilation to produce the end user databases can be performed by a party or entity separate from the map developer. For example, a customer of the map developer, such as a navigation device developer or other end user device developer, can perform compilation on a received geographic database in a delivery format to produce one or more compiled navigation databases.

The processes described herein for detecting joint motion using multiple sensor data may be advantageously implemented via software, hardware (e.g., general processor, Digital Signal Processing (DSP) chip, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGAs), Quantum Computer, etc.), firmware or a combination thereof. Such exemplary hardware for performing the described functions is detailed below.

FIG. 16 illustrates a computer system 1600 upon which an embodiment of the invention may be implemented. Computer system 1600 is programmed (e.g., via computer program code or instructions) to detect joint motion using multiple sensor data as described herein and includes a communication mechanism such as a bus 1610 for passing information between other internal and external components of the computer system 1600. Information (also called data) is represented as a physical expression of a measurable phenomenon, typically electric voltages, but including, in other embodiments, such phenomena as magnetic, electromagnetic, pressure, chemical, biological, molecular, atomic, sub-atomic and quantum interactions. For example, north and south magnetic fields, or a zero and non-zero electric voltage, represent two states (0, 1) of a binary digit (bit). Other phenomena can represent digits of a higher base. A superposition of multiple simultaneous quantum states before measurement represents a quantum bit (qubit). A sequence of one or more digits constitutes digital data that is used to represent a number or code for a character. In some embodiments, information called analog data is represented by a near continuum of measurable values within a particular range.

A bus 1610 includes one or more parallel conductors of information so that information is transferred quickly among devices coupled to the bus 1610. One or more processors 1602 for processing information are coupled with the bus 1610.

A processor 1602 performs a set of operations on information as specified by computer program code related to detecting joint motion using multiple sensor data. The computer program code is a set of instructions or statements providing instructions for the operation of the processor and/or the computer system to perform specified functions. The code, for example, may be written in a computer programming language that is compiled into a native instruction set of the processor. The code may also be written directly using the native instruction set (e.g., machine language). The set of operations include bringing information in from the bus 1610 and placing information on the bus 1610. The set of operations also typically include comparing two or more units of information, shifting positions of units of information, and combining two or more units of information, such as by addition or multiplication or logical operations like OR, exclusive OR (XOR), and AND. Each operation of the set of operations that can be performed by the processor is represented to the processor by information called instructions, such as an operation code of one or more digits. A sequence of operations to be executed by the processor 1602, such as a sequence of operation codes, constitute processor instructions, also called computer system instructions or, simply, computer instructions. Processors may be implemented as mechanical, electrical, magnetic, optical, chemical or quantum components, among others, alone or in combination.

Computer system 1600 also includes a memory 1604 coupled to bus 1610. The memory 1604, such as a random access memory (RAM) or other dynamic storage device, stores information including processor instructions for detecting joint motion using multiple sensor data. Dynamic memory allows information stored therein to be changed by the computer system 1600. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at neighboring addresses. The memory 1604 is also used by the processor 1602 to store temporary values during execution of processor instructions. The computer system 1600 also includes a read only memory (ROM) 1606 or other static storage device coupled to the bus 1610 for storing static information, including instructions, that is not changed by the computer system 1600. Some memory is composed of volatile storage that loses the information stored thereon when power is lost. Also coupled to bus 1610 is a non-volatile (persistent) storage device 1608, such as a magnetic disk, optical disk or flash card, for storing information, including instructions, that persists even when the computer system 1600 is turned off or otherwise loses power.

Information, including instructions for detecting joint motion using multiple sensor data, is provided to the bus 1610 for use by the processor from an external input device 1612, such as a keyboard containing alphanumeric keys operated by a human user, or a sensor. A sensor detects conditions in its vicinity and transforms those detections into physical expression compatible with the measurable phenomenon used to represent information in computer system 1600. Other external devices coupled to bus 1610, used primarily for interacting with humans, include a display device 1614, such as a cathode ray tube (CRT) or a liquid crystal display (LCD), or plasma screen or printer for presenting text or images, and a pointing device 1616, such as a mouse or a trackball or cursor direction keys, or motion sensor, for controlling a position of a small cursor image presented on the display 1614 and issuing commands associated with graphical elements presented on the display 1614. In some embodiments, for example, in embodiments in which the computer system 1600 performs all functions automatically without human input, one or more of external input device 1612, display device 1614 and pointing device 1616 is omitted.

In the illustrated embodiment, special purpose hardware, such as an application specific integrated circuit (ASIC) 1620, is coupled to bus 1610. The special purpose hardware is configured to perform operations not performed by processor 1602 quickly enough for special purposes. Examples of application specific ICs include graphics accelerator cards for generating images for display 1614, cryptographic boards for encrypting and decrypting messages sent over a network, speech recognition, and interfaces to special external devices, such as robotic arms and medical scanning equipment that repeatedly perform some complex sequence of operations that are more efficiently implemented in hardware.

Computer system 1600 also includes one or more instances of a communications interface 1670 coupled to bus 1610. Communication interface 1670 provides a one-way or two-way communication coupling to a variety of external devices that operate with their own processors, such as printers, scanners and external disks. In general, the coupling is with a network link 1678 that is connected to a local network 1680 to which a variety of external devices with their own processors are connected. For example, communication interface 1670 may be a parallel port or a serial port or a universal serial bus (USB) port on a personal computer. In some embodiments, communications interface 1670 is an integrated services digital network (ISDN) card or a digital subscriber line (DSL) card or a telephone modem that provides an information communication connection to a corresponding type of telephone line. In some embodiments, a communication interface 1670 is a cable modem that converts signals on bus 1610 into signals for a communication connection over a coaxial cable or into optical signals for a communication connection over a fiber optic cable. As another example, communications interface 1670 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN, such as Ethernet. Wireless links may also be implemented. For wireless links, the communications interface 1670 sends or receives or both sends and receives electrical, acoustic or electromagnetic signals, including infrared and optical signals, that carry information streams, such as digital data. For example, in wireless handheld devices, such as mobile telephones like cell phones, the communications interface 1670 includes a radio band electromagnetic transmitter and receiver called a radio transceiver. In certain embodiments, the communications interface 1670 enables connection to the communication network 115 for detecting joint motion using multiple sensor data.

The term computer-readable medium is used herein to refer to any medium that participates in providing information to processor 1602, including instructions for execution. Such a medium may take many forms, including, but not limited to, non-volatile media, volatile media and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as storage device 1608. Volatile media include, for example, dynamic memory 1604. Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and carrier waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves. Signals include man-made transient variations in amplitude, frequency, phase, polarization or other physical properties transmitted through the transmission media. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, CDRW, DVD, any other optical medium, punch cards, paper tape, optical mark sheets, any other physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read.

FIG. 17 illustrates a chip set 1700 upon which an embodiment of the invention may be implemented. Chip set 1700 is programmed to detect joint motion using multiple sensor data as described herein and includes, for instance, the processor and memory components described with respect to FIG. 16 incorporated in one or more physical packages (e.g., chips). By way of example, a physical package includes an arrangement of one or more materials, components, and/or wires on a structural assembly (e.g., a baseboard) to provide one or more characteristics such as physical strength, conservation of size, and/or limitation of electrical interaction. It is contemplated that in certain embodiments the chip set can be implemented in a single chip.

In one embodiment, the chip set 1700 includes a communication mechanism such as a bus 1701 for passing information among the components of the chip set 1700. A processor 1703 has connectivity to the bus 1701 to execute instructions and process information stored in, for example, a memory 1705. The processor 1703 may include one or more processing cores with each core configured to perform independently. A multi-core processor enables multiprocessing within a single physical package. Examples of a multi-core processor include two, four, eight, or greater numbers of processing cores. Alternatively or in addition, the processor 1703 may include one or more microprocessors configured in tandem via the bus 1701 to enable independent execution of instructions, pipelining, and multithreading. The processor 1703 may also be accompanied with one or more specialized components to perform certain processing functions and tasks such as one or more digital signal processors (DSP) 1707, or one or more application-specific integrated circuits (ASIC) 1709. A DSP 1707 typically is configured to process real-world signals (e.g., sound) in real time independently of the processor 1703. Similarly, an ASIC 1709 can be configured to performed specialized functions not easily performed by a general purposed processor. Other specialized components to aid in performing the inventive functions described herein include one or more field programmable gate arrays (FPGA) (not shown), one or more controllers (not shown), or one or more other special-purpose computer chips.

The processor 1703 and accompanying components have connectivity to the memory 1705 via the bus 1701. The memory 1705 includes both dynamic memory (e.g., RAM, magnetic disk, writable optical disk, etc.) and static memory (e.g., ROM, CD-ROM, etc.) for storing executable instructions that when executed perform the inventive steps described herein to detect joint motion using multiple sensor data. The memory 1705 also stores the data associated with or generated by the execution of the inventive steps.

FIG. 18 is a diagram of exemplary components of a mobile terminal 1801 (e.g., a UE 101, vehicle 103, or part thereof) capable of operating in the system of FIG. 1, according to one embodiment. Generally, a radio receiver is often defined in terms of front-end and back-end characteristics. The front-end of the receiver encompasses all of the Radio Frequency (RF) circuitry whereas the back-end encompasses all of the base-band processing circuitry. Pertinent internal components of the telephone include a Main Control Unit (MCU) 1803, a Digital Signal Processor (DSP) 1805, and a receiver/transmitter unit including a microphone gain control unit and a speaker gain control unit. A main display unit 1807 provides a display to the user in support of various applications and mobile station functions that offer automatic contact matching. An audio function circuitry 1809 includes a microphone 1811 and microphone amplifier that amplifies the speech signal output from the microphone 1811. The amplified speech signal output from the microphone 1811 is fed to a coder/decoder (CODEC) 1813.

A radio section 1815 amplifies power and converts frequency in order to communicate with a base station, which is included in a mobile communication system, via antenna 1817. The power amplifier (PA) 1819 and the transmitter/modulation circuitry are operationally responsive to the MCU 1803, with an output from the PA 1819 coupled to the duplexer 1821 or circulator or antenna switch, as known in the art. The PA 1819 also couples to a battery interface and power control unit 1820.

In use, a user of mobile station 1801 speaks into the microphone 1811 and his or her voice along with any detected background noise is converted into an analog voltage. The analog voltage is then converted into a digital signal through the Analog to Digital Converter (ADC) 1823. The control unit 1803 routes the digital signal into the DSP 1805 for processing therein, such as speech encoding, channel encoding, encrypting, and interleaving. In one embodiment, the processed voice signals are encoded, by units not separately shown, using a cellular transmission protocol such as global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS), etc., as well as any other suitable wireless medium, e.g., microwave access (WiMAX), Long Term Evolution (LTE) networks, code division multiple access (CDMA), wireless fidelity (WiFi), satellite, and the like.

The encoded signals are then routed to an equalizer 1825 for compensation of any frequency-dependent impairments that occur during transmission though the air such as phase and amplitude distortion. After equalizing the bit stream, the modulator 1827 combines the signal with a RF signal generated in the RF interface 1829. The modulator 1827 generates a sine wave by way of frequency or phase modulation. In order to prepare the signal for transmission, an up-converter 1831 combines the sine wave output from the modulator 1827 with another sine wave generated by a synthesizer 1833 to achieve the desired frequency of transmission. The signal is then sent through a PA 1819 to increase the signal to an appropriate power level. In practical systems, the PA 1819 acts as a variable gain amplifier whose gain is controlled by the DSP 1805 from information received from a network base station. The signal is then filtered within the duplexer 1821 and optionally sent to an antenna coupler 1835 to match impedances to provide maximum power transfer. Finally, the signal is transmitted via antenna 1817 to a local base station. An automatic gain control (AGC) can be supplied to control the gain of the final stages of the receiver. The signals may be forwarded from there to a remote telephone which may be another cellular telephone, other mobile phone or a land-line connected to a Public Switched Telephone Network (PSTN), or other telephony networks.

Voice signals transmitted to the mobile station 1801 are received via antenna 1817 and immediately amplified by a low noise amplifier (LNA) 1837. A down-converter 1839 lowers the carrier frequency while the demodulator 1841 strips away the RF leaving only a digital bit stream. The signal then goes through the equalizer 1825 and is processed by the DSP 1805. A Digital to Analog Converter (DAC) 1843 converts the signal and the resulting output is transmitted to the user through the speaker 1845, all under control of a Main Control Unit (MCU) 1803—which can be implemented as a Central Processing Unit (CPU) (not shown).

The MCU 1803 receives various signals including input signals from the keyboard 1847. The keyboard 1847 and/or the MCU 1803 in combination with other user input components (e.g., the microphone 1811) comprise a user interface circuitry for managing user input. The MCU 1803 runs a user interface software to facilitate user control of at least some functions of the mobile station 1801 to detect joint motion using multiple sensor data. The MCU 1803 also delivers a display command and a switch command to the display 1807 and to the speech output switching controller, respectively. Further, the MCU 1803 exchanges information with the DSP 1805 and can access an optionally incorporated SIM card 1849 and a memory 1851. In addition, the MCU 1803 executes various control functions required of the station. The DSP 1805 may, depending upon the implementation, perform any of a variety of conventional digital processing functions on the voice signals. Additionally, DSP 1805 determines the background noise level of the local environment from the signals detected by microphone 1811 and sets the gain of microphone 1811 to a level selected to compensate for the natural tendency of the user of the mobile station 1801.

The CODEC 1813 includes the ADC 1823 and DAC 1843. The memory 1851 stores various data including call incoming tone data and is capable of storing other data including music data received via, e.g., the global Internet. The software module could reside in RAM memory, flash memory, registers, or any other form of writable computer-readable storage medium known in the art including non-transitory computer-readable storage medium. For example, the memory device 1851 may be, but not limited to, a single memory, CD, DVD, ROM, RAM, EEPROM, optical storage, or any other non-volatile or non-transitory storage medium capable of storing digital data.

An optionally incorporated SIM card 1849 carries, for instance, important information, such as the cellular phone number, the carrier supplying service, subscription details, and security information. The SIM card 1849 serves primarily to identify the mobile station 1801 on a radio network. The card 1849 also contains a memory for storing a personal telephone number registry, text messages, and user specific mobile station settings.

While the invention has been described in connection with a number of embodiments and implementations, the invention is not so limited but covers various obvious modifications and equivalent arrangements, which fall within the purview of the appended claims. Although features of the invention are expressed in certain combinations among the claims, it is contemplated that these features can be arranged in any combination and order. 

What is claimed is:
 1. A method comprising: retrieving a joint motion prediction indicating whether at least two devices are traveling in a same transportation vehicle, wherein the joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types, and wherein each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction; and initiating a ride-sharing function for respective users of the at least two devices based on the joint motion prediction, wherein the ride-sharing function comprises automatically detecting that the respective users have taken a correct ride event booked with a ride-sharing service.
 2. The method of claim 1, wherein the ride-sharing function comprises: automatically detecting that a ride event of a ride-sharing service has taken place between the respective users; and initiating a payment event based on the detected ride event.
 3. The method of claim 1, wherein the respective users are part of a group, and wherein the ride-sharing function comprises: automatically detecting that all of the respective users of the group are in the same transportation vehicle for a group ride.
 4. The method of claim 1, wherein the same transportation vehicle is used for a first leg of a trip, and wherein the ride-sharing function comprises: recommending to the respective users to continue a second leg of the trip together by sharing another transportation vehicle.
 5. The method of claim 1, wherein the ride-sharing function comprises: determining a pickup location, a drop-off location, or a combination thereof of at least one of the respective users.
 6. The method of claim 1, wherein the ride-sharing function comprises: initiating a classification of a trip of the same transportation vehicle as a ride-sharing drive event or a non-ride-sharing drive event.
 7. The method of claim 6, wherein the ride-sharing function further comprises: automatically applying either a ride-sharing insurance policy or a non-ride-sharing insurance policy to the trip based on the classification.
 8. The method of claim 1, wherein the ride-sharing function comprises: determining that a cancellation event for a trip of the same transportation vehicle is fraudulent.
 9. An apparatus comprising: at least one processor; and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following, retrieve a joint motion prediction indicating whether at least two devices are traveling in a same transportation vehicle, wherein the joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types, and wherein each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction; and initiate a ride-sharing function for respective users of the at least two devices based on the joint motion prediction, wherein the ride-sharing function comprises automatically detecting that the respective users have taken a correct ride event booked with a ride-sharing service.
 10. The apparatus of claim 9, wherein the ride-sharing function causes the apparatus to: automatically detect that a ride event of a ride-sharing service has taken place between the respective users; and initiate a payment event based on the detected ride event.
 11. The apparatus of claim 9, wherein the ride-sharing function causes the apparatus to: automatically detect that the respective uses have taken a correct ride event booked with a ride-sharing service.
 12. The apparatus of claim 9, wherein the respective users are part of a group, and wherein the ride-sharing function causes the apparatus to: automatically detect that all of the respective users of the group are in the same transportation vehicle for a group ride.
 13. The apparatus of claim 9, wherein the same transportation vehicle is used for a first leg of a trip, and wherein the ride-sharing function causes the apparatus to: recommend to the respective users to continue a second leg of the trip together by sharing another transportation vehicle.
 14. The apparatus of claim 9, wherein the ride-sharing function comprises: determining a pickup location, a drop-off location, or a combination thereof of at least one of the respective users.
 15. A non-transitory computer-readable storage medium carrying one or more sequences of one or more instructions which, when executed by one or more processors, cause an apparatus to perform: retrieving a joint motion prediction indicating whether at least two devices are traveling in a same transportation vehicle, wherein the joint motion prediction is computed based on sensor data collected from the at least two devices using at least one sensor type from among a plurality of sensor types, and wherein each sensor type of the plurality of sensor types is associated with a respective joint motion classifier configured to compute a sensor-type joint motion prediction that is used for generating the joint motion prediction; and initiating a ride-sharing function for respective users of the at least two devices based on the joint motion prediction, wherein the ride-sharing function comprises automatically detecting that the respective users have taken a correct ride event booked with a ride-sharing service.
 16. The non-transitory computer-readable storage medium of claim 15, wherein the ride-sharing function causes the apparatus to perform: automatically detecting that a ride event of a ride-sharing service has taken place between the respective users; and initiating a payment event based on the detected ride event.
 17. The non-transitory computer-readable storage medium of claim 15, wherein the respective users are part of a group, and wherein the ride-sharing function causes the apparatus to perform: automatically detecting that all of the respective users of the group are in the same transportation vehicle for a group ride.
 18. The non-transitory computer-readable storage medium of claim 15, wherein the same transportation vehicle is used for a first leg of a trip, and wherein the ride-sharing function causes the apparatus to perform: recommending to the respective users to continue a second leg of the trip together by sharing another transportation vehicle. 